Blue Prism 6.2.1: May 2018

A fix has been applied whereby, following an application server service restart, scheduled jobs failed to run. If the schedule was restarted manually using the Run Now feature, the scheduler reinitializes. This has now been fixed so that all schedules restart as expected.

A schedule configured to run a number of tasks in sequence was attempting to start all tasks simultaneously, resulting in a KeyNotFoundException. This error is now prevented and the schedule executes jobs correctly.

An issue that may have caused an upgrade failure if the default dbo schema was not used in the database has been addressed by removing hard-coded references to this schema within the 6.2 database scripts. This issue only affected environments created using or being upgraded to version 6.2. database objects, incorrectly created with a dbo schema when upgrading to 6.2, will be automatically updated to use the appropriate schema when applying a database script containing this fix.

When carrying out a database upgrade, the error reporting has been improved to provide greater visibility of the specific change that is presenting the issue.

A fix has been implemented to address a prolonged connectivity issue between the resource and the application server which caused the resource to stop attempting to re-establish the connection. This made it unavailable within the Blue Prism environment until the runtime resource is restarted.

A fix has been applied so that runtime resources correctly reconnect following a SQL Server database restart. Previously, an issue introduced in 6.0, meant that when a resource attempted to reconnect to the database either directly or via an application server, an error reported that the listener was offline and tried to restart every two minutes even though it was already online.

The following improvements have been made to WCF connectivity:

• The data packets generated when creating or updating schedules over a WCF server connection have been optimized to improve performance and reduce the potential for SQL timeouts.
• An update to the re-connection mechanism has been applied to cater for situations where, following an interruption in the connection between a runtime and the application server, the runtime reported that it was unable to calculate the run mode of certain processes.

An issue that was preventing some resources reconnecting following a network outage on the application server has been fixed. The resources failed to authenticate and log in after a network outage of 90 seconds or more between the resources and the Application when using Blue Prism native authentication. The following error was produced on affected resources:

Failed to shutdown Login Agent Resource on Port:0
Unauthorized: User not logged in

It is now possible to select the parent region when using a relative search mode with a coordinate-based region.

It is now possible to alter the process behavior when applying updates to a collection that was copied from an inner, or nested collection. This optional change affects the relationship between the original and nested collection as data is passed by value, rather than by reference, so that changes are not reflected in the original collection. This is implemented on a per process basis and requires a manual update to the process XML, via export and re-import.

For advice on applying this change, see the associated Knowledge Base article article.

When using Active Accessibility, it is now possible to select any item from a combo box drop-down list irrespective of whether the item is not currently visible due to being presented within a scroll list. Prior to this fix, if scrolling through the drop-down was required to locate an item, an error occurred.